WG and TF updates #1018
WG and TF updates #1018
Conversation
✅ Deploy Preview for wai-website ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
- abbreviations (expanding some) - simplify summary sentence (without removing or changing meaning) and format as a list for readability - add section with quick link to Admin home page - remove generic headings - add headings / structure content meaningfully under headings that match key words in the information - make headings sentence case - remove capital letters from nouns that are not proper nouns - Make link text slightly more descriptive, including signaling if moving away from WAI to a different sub-site. - Add / correct URLs - remove passive tense - use plain language - make sentences more concise - make list items consist of only one sentence per item (best practice) - fix typos
There was a problem hiding this comment.
Hi @tamsinewing555,
Thanks for this. I like your alternative approach that avoids lots of headings with a single link. Thanks for taking the time to come up with a solution to my concerns!
There are a few wee things that are slightly off. I have put comments into the PR - ping me if you are unable to find them.
PDF is a common abbreviation that has become part of the English language - it's better understood than the expanded term
|
@shawna-slh, @remibetin The new structure that we have includes exposing TF Work Statements in the left hand navigation. This results in a forth level of sidebar navigation which looks like: 
Thoughts? We have had this problem before with How People with Disabilities Use the Web but got round it by rejigging the approach slightly. For the case of TF Work Statements I am not sure there is an easy alternative - I did think of pulling TFs to the same level as Groups but I don't think that is appropriate. |
I also think it's hard to find an easy alternative. The current hierarchy is probably deep, but I think it is clear. I am more concerned by the missing secondary navigation and breadcrumbs in the current work statements pages in that regard. On these pages, users have no clues about where they are and where to go next. See for example: https://www.w3.org/WAI/about/groups/task-forces/conformance-testing/work-statement/ The way the menus are designed is another thing. We could probably improve that: the indentation becomes more and more important in the secondary navigation when we go deep. Although finding the right consistent approach would require substantial effort. A possibility among others: W3C main site is using a mega menu, and section navigation. For the moment, I would keep your proposed structure and make sure the breadcrumbs and secondary navigation are indeed displayed on fourth level pages. |
|
Another thought: I am not sure finding a Task force work statement is a top task for most users of the WAI website. I would imagine people looking for a task force work statement would even prefer to browse the "Discover W3C groups" section of the W3C website and find the work statement of any W3C task force/ In this page for example: https://www.w3.org/groups/tf/wcag-act/ |
Work statements aren't really a required feature of Task Forces. Based on that it probably wouldn't be appropriate to request this change to the core Group pages. |
There will be a couple of PRs to deal with this: one in wai-website-theme to handle the changes to the sidenav and one in the wai-website-data to handle the new navigation.yml. As well as this one. |
preview